Published on Multilingual Online Translation (http://www.molto-project.eu)

Home > Printer-friendly > Book > Export > Html > 850 > D1.1 Work plan for MOLTO

D1.1 Work plan for MOLTO

Contract No.:

FP7-ICT-247914

Project full title:

MOLTO [1] - Multilingual Online Translation

Deliverable:

D1.1. Work plan for MOLTO [1]

Security (distribution level):

Confidential

Contractual date of delivery:

M1

Actual date of delivery:

1 April 2010

Type:

Report

Status & version:

Final (evolving document)

Author(s):

A. Ranta et al.

Task responsible:

UGOT [2]

Other contributors:

Abstract

Detailed work plan for internal use of the consortium.

This is an evolving description of the work plan of MOLTO [1], divided in work packages and in tasks. The document is meant to track what the MOLTO [1] Consortium is planning to do, what it has completed so far and the status of the ongoing research. It is the responsibility of the work package leader to enter tasks and to keep them up to date so as to reflect the work done by the group.

WP1: Management

Detailed workplan for WP1 [3]

A number of management tasks are entitled to the coordinator: e.g. - collecting information from partners,

- reviewing and submitting information on the progress of the project as well as reports and other deliverables to EC; - preparation of meetings, - proposing the decisions and preparing the agenda of the SG, - chairing of the SG meetings and monitoring the implementation of decisions taken at the meetings; - presenting the results of the consortium and serving as the secretary in the meetings; - administering the EC financial contribution and fulfilling other financial tasks, - maintaining the project's website etc.

According to the Grant Agreement, Annex II, management of the consortium activities includes:

- maintenance of the consortium agreement, if it is obligatory,

- the overall legal, ethical, financial and administrative management including, for each of the beneficiaries, the obtaining of the certificates on the financial statements and on the methodology and costs relating to financial audits and technical reviews,

- implementation of competitive calls by the consortium for the participation of new beneficiaries, where required by Annex I of this grant agreement,

- any other management activities foreseen by the annexes, except coordination of research and technological development activities.

Associate tasks to workpackages

ID:

1.1

Workpackage:

Management [3]

Task leader:

aarne.ranta [4]

Assignees:

olga.caprotti [5]

Relevant Deliverables:

Dissemination plan, with monitoring and assessment [6]

Status:

Completed

Timeframe:

Mar 2010 - Apr 2010

Completed on:

25 March, 2010 - 23:00

In order to get an overview of the workpackage: - add a view of the associated tasks - add a view of the deliverables

Create content type "deliverable"

ID:

1.2

Workpackage:

Management [3]

Task leader:

aarne.ranta [4]

Assignees:

olga.caprotti [5]

Status:

Completed

Create an admin type "deliverable" to collect the info on due deliverable so that they can be tracked on the calendar and in the workpackage's description.

See list of all deliverables [7]

WP2: Grammar Developer’s Tools

The grammar developer's tools are divided to two kinds of tasks:

- GF [8] grammar compiler API

- actual tools implemented by using the API

The workplan for the first six months concerns mostly the API, with the main actual tool being the GF [8] Shell, which is a line-based grammar development tool. It is a powerful tool since it enables scripting, but it is not integrated with other working environments. The most important other environment will be web-based access to the grammar compiler.

Note that most discussions on GF [8] are public at http://code.google.com/p/grammatical-framework/ [9].

Here follows the work plan, with tasks assigned to sites and approximate months.

Improving the Resource Grammar Library API and its documentation

ID:

2.10

Workpackage:

Grammar Developer’s Tools [10]

Task leader:

aarne.ranta [4]

Assignees:

ramona.enache [11]

Relevant Deliverables:

GF Grammar Compiler API [12]

Dependencies:

Designing the API and writing its documentation [13]

Status:

Ongoing

Timeframe:

Mar 2010

Documentation of GF [8] is hosted on Google Code at http://code.google.com/p/grammatical-framework/ [9]

There is a wiki cover page [14] for the Resource Grammar Library API and an online version at http://www.grammaticalframework.org/compiler-api/ [15].

Designing the API and writing its documentation

ID:

2.5

Workpackage:

Grammar Developer’s Tools [10]

Task leader:

aarne.ranta [4]

Assignees:

krasimir.angelov [16]

Status:

Completed

Timeframe:

Mar 2010 - Aug 2010

Completed on:

1 October, 2011 (All day)

The GF [8] API design will take into account the following requirements:

- programming environment eg Eclipse, XCode, NotePad++, Web etc

- standard formats for I/O

- ....

The documentation is being hosted at the GF [8] website.

Example-based grammar writing

ID:

2.2

Workpackage:

Grammar Developer’s Tools [10]

Task leader:

ramona.enache [11]

Assignees:

aarne.ranta [4]

Relevant Deliverables:

Grammar IDE [17]

Status:

Ongoing

Timeframe:

Jul 2010 - Sep 2010

What we mean by example based grammar writing.

Current status is proof of concept: it is possible to load example based grammar and to compile it.

Need to do: - ....

GF runtime in C

ID:

2.11

Workpackage:

Grammar Developer’s Tools [10]

Task leader:

lauri.alanko [18]

Assignees:

jordi.saludes [19]

Assignees:

krasimir.angelov [16]

Assignees:

lauri.alanko [18]

Status:

Ongoing

Timeframe:

Apr 2010

Overview

The runtime is the part of the GF [8] system that implements parsing and linearization of texts based on a PGF grammar that has been produced by the GF [8] compiler.

The standard GF [8] runtime is written in Haskell like the rest of the system. Unfortunately this results in a large memory footprint and possibly also portability problems, which preclude its use in certain applications.

The goal of the current task is to reimplement the GF [8] runtime as a pure C library. This C library can then hopefully be used in some situations where the Haskell-based runtime would be unwieldy.

Goals

- Small memory footprint

- Better efficiency than the Haskell version

- Portable

- No dependencies on languages other than C

- Only depends on widely portable libraries

Status

The development of the C runtime is done in the MOLTO [1] Subversion repository. The current version can be checked out at the location svn://molto-project.eu/libpgf/trunk/ .

As of currently (2010-09-29), the library only supports reading in PGF files and printing them out in a (nearly) human-readable YAML [20] format.

Instructions

There is no user documentation yet, nor is the code itself yet properly commented. However, the project is a standard GNU Autotools [21] -based library, so building it is straightforward. Make sure you have reasonably recent versions of GNU Autotools and GLib [22] installed, and then:

svn co svn://molto-project.eu/libpgf/trunk/ libpgf

cd libpgf

autoreconf -i

./configure

make

If everything works okay, you should now have a pgf2yaml executable, which you can run as a filter: ./pgf2yaml < .../foo.pgf > foo.yaml

The resulting YAML file is not nicely formatted, but it can be parsed and reformatted by other YAML tools. For instance, in Python with PyYAML [23], you can do the following:

import yaml

yaml.dump(yaml.load(open('foo.yaml')), open('foo-pretty.yaml', 'w'))

The resulting file should be useful for examining the structure of the PGF file. Unfortunately the ordering of fields is not preserved, though.

Morphology server and its API

ID:

2.3

Workpackage:

Grammar Developer’s Tools [10]

Task leader:

aarne.ranta [4]

Assignees:

aarne.ranta [4]

Assignees:

krasimir.angelov [16]

Relevant Deliverables:

Grammar IDE [17]

Status:

Planned

Timeframe:

Aug 2010 - Oct 2010

The compiler API must be used by the morphology server.

Plugin to Python NLTK

ID:

2.8

Workpackage:

Grammar Developer’s Tools [10]

Task leader:

jordi.saludes [19]

Assignees:

jordi.saludes [19]

Status:

Completed

To develop a python plugin for gf (based on the planned C plugin) and connect it to relevant parts of the Natural Language Toolkit (http://www.nltk.org/ [24])

Subtasks

2.8.1 Develop python bindings to gf.

2.8.2 nltk integration.

GF python bindings

Using the GF [8] python bindings

This is how to use some of the functionalities of the GF [8] shell inside Python.

Installation

Due to some ghc glitch, it only builds on Linux.

You'll need the source distribution of GF [8], ghc [25] and the Python development files[1]. Then, go to the python bindings folder and build it:

cd GF [8]/contrib/py-bindings

make

It will build a shared library (gf.so) that you can import and use into Python as shown below.

Testing installation

To test if it works correctly, type:

python -m doctest example.rst

Examples

Loading a pgf file

First you must import the library:

% import gf

then load a PGF file, like this tiny example:

% pgf = gf.read_pgf("Query.pgf")

We could ask for the supported languages:

% pgf.languages()

[QueryEng, QuerySpa]

The start category of the PGF module is:

% pgf.startcat()

Question

Parsing and linearizing

Let's us save the languages for later:

% eng,spa = pgf.languages()

These are opaque objects, not strings:

% type(eng)

(type 'gf.lang')

and must be used when parsing:

% pgf.parse(eng, "is 42 prime")

[Prime (Number 42)]

Yes, I know it should have a '?' at the end, but there is not support for other lexers at this time.

Notice that parsing returns a list of gf trees. Let's save it and linearize it in Spanish:

% t = pgf.parse(eng, "is 42 prime")

% pgf.linearize(spa, t[0])

'42 es primo'

(which is not, but there is a '?' lacking at the end, remember?)

Getting parsing completions

One of the good things of the GF [8] shell is that it suggests you which tokens can continue the line you are composing.

We got this also in the bindings. Suppose we have no idea on how to start:

% pgf.complete(eng, "")

['is']

so, there is only a sensible thing to put in. Let's continue:

% pgf.complete(eng, "is ")

[]

Is it important to note the blank space at the end, otherwise we get it again:

% pgf.complete(eng, "is")

['is']

But, how come that nothing is suggested at "is "? At the current point, a literal integer is expected, so GF [8] would have to present an infinite list of alternatives. I cannot blame it for refusing to do so.

% pgf.complete(eng, "is 42 ")

['even', 'odd', 'prime']

Good. I will go for 'even', just to be in the safe side:

% pgf.complete(eng, "is 42 even ")

[]

Nothing again, but this time the phrase is complete. Let us check it by parsing:

% pgf.parse(eng, "is 42 even")

[Even (Number 42)]

Deconstructing gf trees

We store the last result and ask for its type:

% t = pgf.parse(eng, "is 42 even")[0]

% type(t)

(type 'gf.tree')

What's inside this tree? We use unapply for that:

% t.unapply()

[Even, Number 42]

This method returns a list with the head of the fun judgement and its arguments:

% map(type, _)

[(type 'gf.cid'), (type 'gf.expr')]

Notice the argument is again a tree (gf.tree or gf.expr, it is all the same here.)

% t.unapply()[1]

Number 42

We will repeat the trick with it now:

% t.unapply()[1].unapply()

[Number, 42]

and again, the same structure shows up:

% map(type, _)

[(type 'gf.cid'), (type 'gf.expr')]

One more time, just to get to the bottom of it:

% t.unapply()[1].unapply()[1].unapply()

42

but now it is an actual number:

% type(_)

(type 'int')

We ended with a full decomposed fun judgement.

1. In Ubuntu I got it by installing the package python-all-dev. ↩

Refactoring the grammar compiler code base (to improve reusability)

ID:

2.1

Workpackage:

Grammar Developer’s Tools [10]

Task leader:

aarne.ranta [4]

Assignees:

krasimir.angelov [16]

Status:

Assigned

Timeframe:

Mar 2010 - Jul 2010

Here a slighly better description with eventually relevant links to sw, documentation etc.

Release of GF 3.2

ID:

2.4

Workpackage:

Grammar Developer’s Tools [10]

Task leader:

aarne.ranta [4]

Assignees:

aarne.ranta [4]

Assignees:

krasimir.angelov [16]

Status:

Ongoing

Timeframe:

Mar 2010 - Dec 2010

Major features:

- pgf format is updated and documented in the wiki

- completed runtime type checker for dependent types

- parsing with dependent types

- on-line parsing

- type-error reporting

- exhaustive generation of ASTs (also via lambda prolog)

- probabilities in the abstract syntax

- random generation guided by probability

- parse results ranked by probability

- example based grammar generation (extra script)

New languages:

- Urdu, complete resource grammar

- Turkish, complete morphology

- Amharic, complete resource grammar

- Punjabi, complete morphology

Web-based grammar development environment (version 1)

ID:

2.6

Workpackage:

Grammar Developer’s Tools [10]

Task leader:

aarne.ranta [4]

Assignees:

krasimir.angelov [16]

Assignees:

thomas.hallgren [26]

Relevant Deliverables:

Grammar IDE [17]

Dependencies:

Release of GF 3.2 [27]

Status:

Ongoing

Timeframe:

Aug 2010 - Mar 2011

Prototype

Web-based tools for grammarians: http://www.grammaticalframework.org/demos/gfse/ [28]

Similar work

Look into online IDE platforms [29], like Kodingen and CodeRun.

There is work for Ajax-based code editors, eg Ymacs [30], which could be useful since there is a GF [8] mode for emacs already (where?).

The emacs mode can now be found in http://www.grammaticalframework.org/src/tools/gf.el [31] (note by Aarne)

There is also a Mozilla project, Bespin [32], to build a web-based editor extensible by javascript.

Also - check Orc [33], yet another online IDE for a new language, using CodeMirror [34] as editor.

Integrating probabilities in GF and PGF

ID:

2.8

Workpackage:

Grammar Developer’s Tools [10]

Task leader:

aarne.ranta [4]

Assignees:

aarne.ranta [4]

Status:

Planned

Timeframe:

Oct 2010 - Dec 2010

Design and intergrate probabilistic features to GF [8] and PGF.

Extend planning here.

Integration with ontology tools

ID:

2.9

Workpackage:

Grammar Developer’s Tools [10]

Task leader:

aarne.ranta [4]

Assignees:

aarne.ranta [4]

Assignees:

borislav.popov [35]

Assignees:

lauri.carlson [36]

Status:

Planned

Finale phase of the work planned in this workpackage. Exact scheduling to be defined.

On-line extension of PGF with new words

ID:

2.7

Workpackage:

Grammar Developer’s Tools [10]

Task leader:

aarne.ranta [4]

Assignees:

krasimir.angelov [16]

Status:

Planned

Timeframe:

Aug 2010 - Jan 2011

Adding the possibility to dynamically add new words to lexicons "linked" in compiled grammars.

WP3: Translator's Tools

To be entered for M7 - M30.

WP4: Knowledge Engineering

knowledge representation infrastructure (D4.1, by Ontotext [37]);

aligned semantic models and instance bases (D4.2, by Ontotext [37] and UHEL [38]);

two-way grammar-ontology and NL (Natural Language) to ontology interoperability (D4.3, by Ontotext [37] and UGOT [2]).

M1-M6 plan

- all partners send informal answers of the questions above & anything additional that has been missed in the questions (questionnaire)[/node/896]

- decide on the best server location (on site / rented)

- Ontotext [37] to provide a description of what is the planned initial infrastructure for KE

- Ontotext [37] to describe more about the LOD data sets and give the LDSR link

- UHEL [38] to indicate their ideas on the KE WP, data sets and participation

- provide examples of entity descriptions in WKB

- first attempts on NL queries based on the WKB; put examples of the entity description constructs and then decide next steps with UGOT [2]/UHEL [38];

- discuss feasibility of creating a NL interface for SPARQL (or a subset)

- provide examples of entity descriptions in WKB

- KE infrastructure in place

- decide on initial data sets with the partners; consider one or many instances

- KE infrastructure loaded with initial data sets

- navigation and search web UI over KEI

- results of the first experiences on ontology to grammar interoperability

- M4.1 - Knowledge representation - Retrieval access provided infrastructure to the consortium

- report for M1-M6

- plan for M6-M12

M6-M12 plan

- analyze the needs of autocompletetion and implement scalable solution for it

- work on transformation from natural language to sparql

- report for M6-M12

- plan for M6-M12

M12-M18 plan

- experiment with different ontologies

- write D4.2

- work on verbalization of the results from the semantic repository search

- finalize the D4.3 prototype

- report for M12-M18

- plan for M12-M18

M18-M24 plan

- support the work on other workpakages in the sphere of grammar-ontology interoperability

- report for M18-M24

Process & General Considerations

- we'd like all info to be available on the wiki, incl. notes, decisions, status of the components, docs

- SVN

- consider a backlog for the entire project/ each WP

- consider periodic development/delivery cycles

- consider regular telecons/skype conferences - once a month at least

- make application ideas backlog at the wiki

Knowledge Engineering Infrastructure in place

According to the plan http://www.molto-project.eu/node/858 [39] the Knowledge Engineering Infrastructure has been realeased. It is accessible here [40]. We have imported an exemplary initial data set containing information for different persons, organizations, locations.

To execute a SPARQL query [41] to the data set, click "SPARQL Query" and for exemple try the following query without the backslashes (\)

prefix rdf:<\http://www.w3.org/1999/02/22-rdf-syntax-ns#> prefix rdfs:<\http://www.w3.org/2000/01/rdf-schema#> prefix prt:<\http://proton.semanticweb.org/2006/05/protont#> select distinct ?l where { ?s rdf:type prt:Organization ; rdfs:label ?l . }

It should return the names of all organizations stored in the data set.

The Knowledge Engineering Infrastructure could be extended with new data sets if new data sets are available, see http://www.molto-project.eu/node/858 [39], http://www.molto-project.eu/node/896 [42] and http://www.molto-project.eu/node/948 [43].

WP5: Statistical and Robust Translation

here a better task description

WP6: Case Study Mathematics

Mathematical grammars developed using GF [8] for the WebALT project (eContent 22253) allow us to generate multilingual simple drills for high school students and university freshmen. These grammars will be the starting point aiming at extending coverage to word problems, the ones that require the student to first model a situation and then to manipulate the mathematical model to obtain a solution.

The UPC [44] team, being a main actor in the past developing of gf mathematical grammars and having ample experience in mathematics teaching, will be in charge of the tasks in this work package with help from UGOT [2] on technical aspects of GF [8] and possibly Ontotext [37] on ontology representation and handling.

Meeting for work planning

ID:

6.0

Workpackage:

Case Study: Mathematics [45]

Task leader:

jordi.saludes [19]

Assignees:

jordi.saludes [19]

Assignees:

Sebastian Xambo [46]

Status:

Hold

Omega, room 409B

Delineate the schedule for WP6 [45].

Gather examples of word problems

ID:

6.1

Workpackage:

Case Study: Mathematics [45]

Task leader:

Sebastian Xambo [46]

Assignees:

jordi.saludes [19]

Assignees:

Sebastian Xambo [46]

Status:

Planned

Compile examples of word problems, mainly high school algebra problems to use as samples for the following tasks.

State of the art on mathematical and ontological reasoning

ID:

6.2

Workpackage:

Case Study: Mathematics [45]

Task leader:

jordi.saludes [19]

Assignees:

jordi.saludes [19]

Status:

Planned

It will be required to reason on equations and statements proposed by the student, so we will need to review to what extend an automatic reasoner could deal with student input of this sort and how the system behavior could be designed to degrade gracefully in order to keep the student interaction going.

Make WebALT grammars modular

ID:

6.3

Workpackage:

Case Study: Mathematics [45]

Task leader:

jordi.saludes [19]

Assignees:

jordi.saludes [19]

Assignees:

Sebastian Xambo [46]

Relevant Deliverables:

Simple drill grammar library [47]

Status:

Ongoing

Timeframe:

Jul 2010

In the framework of the WebALT project a gf grammar library was developed for generating simple mathematical drills in a variety of languages. The legal status of this library has recently changed to LGPL [48], making it suitable to be the starting point for the language services demanded by this work package. To achieve a better degree of interchangeability it is required to organize the existing code into modules, remove redundancies and lay them in a way acceptable for easy lexicon enhancement by way of the grammar developer’s tools of work package 2, WP2 [10].

Commanding GF library

ID:

6.4

Workpackage:

Case Study: Mathematics [45]

Task leader:

jordi.saludes [19]

Assignees:

jordi.saludes [19]

Dependencies:

Make WebALT grammars modular [49]

Status:

Planned

Writing a gf grammar for commanding a generic computer algebra system (CAS) by natural language imperative sentences. Concrete grammars adapted to the CAS at hand. Depends on work package 2 WP2 [10].

Module for driving a CAS by natural language commands

ID:

6.5

Workpackage:

Case Study: Mathematics [45]

Task leader:

jordi.saludes [19]

Assignees:

jordi.saludes [19]

Assignees:

Sebastian Xambo [46]

Dependencies:

Commanding GF library [50]

Status:

Planned

Integrate the commanding library into a component to transform the issued commands to the CAS.

Objects and properties GF library

ID:

6.6

Workpackage:

Case Study: Mathematics [45]

Task leader:

jordi.saludes [19]

Assignees:

jordi.saludes [19]

Status:

Planned

Gf grammar library able to generate natural language sentences corresponding to objects and relations of the word problem. It must be able to parse simple questions related to the word problem domain into predicates. Depends on work package 2 and probably work package 4.

Module for semi-automatic reasoning

ID:

6.7

Workpackage:

Case Study: Mathematics [45]

Task leader:

jordi.saludes [19]

Assignees:

jordi.saludes [19]

Status:

Planned

Automated reasoning is needed to assess the soundness of the model proposed by the student and to answer his/her questions. This requires adding small ontologies describing the word problem, including:

- Data present in the problem statement;

- Additional world knowledge to make reasoning possible.

Add State of the Art study here.

Set theory reasoning of the ducks and rabbits problem

Some time ago I managed to build a theory supporting the Farm problem in Isabelle/HOL (attached below)

I wasn't expecting such a toil but lack of detailed documentation and a wicked simplifier made my life miserable for a whole week.

Assumptions

It is based on 3 sets:

- Being in the farm (farm)

- Being a duck

- Being a rabbit

- and a function: is_leg_of : leg → animal.

As axioms, we have:

Ground knowledge axioms

- Rabbits have 4 legs.

- Ducks have 2 legs.

Problem axioms

- All animals in the farm are rabbits or ducks.

- There are 100 animals in the farm.

- There are 260 legs in the farm

Extra axioms

That is, facts that are implicitely known but you need to state for Isabelle with Main theory to work:

- Rabbits and ducks are finite

- Rabbits and ducks are disjoint

Variables and equations

Let R be the number of rabbits in the farm and D the number of ducks in the farm. With the preceding axioms, we were able to produce Isabelle-certified proofs that

R + D = 100

and

2*D + 4*R = 260

and then deduce that R=30 and D=70.

Attachment

Size

Farm.thy [51]

5.67 KB

Integration into dialog manager

ID:

6.8

Workpackage:

Case Study: Mathematics [45]

Task leader:

jordi.saludes [19]

Assignees:

jordi.saludes [19]

Status:

Planned

In particular, objects will be annotated by natural language noun-phrases and equations by sentences. These annotations will be parsed into GF [8] interlingua and will be used whenever language generation related to the problem was needed.

WP7: Case Study Patents

The work will start with the provision of user requirements (WP9 [52]) and the preparation of a parallel patent corpus (EPO) to fuel the training of statistical MT (UPC [44]). In parallel UGOT [2] will work on grammars covering the domain and subsequently, together with UPC [44], apply the hybrid (WP2 [10], WP5 [53]) MT on abstracts and claims. Ontotext [37] will provide semantic infrastructure with loaded existing structured data sets (WP4 [54]) from the patent domain (IPC, patent ontology, bio-medical and pharmaceutical knowledge bases, e.g. LLD). Based on the use case requirements, Ontotext [37] will build a prototype (D7.1, D7.2) exposing multiple cross-lingual retrieval paradigms and MT of patent sections. The accuracy will be regularly evaluated through both automatic (e.g. BLEU scoring) and human based (e.g. TAUS) means (WP9 [52]).

Task List

The work package is split into 9 major tasks as follows:

- Task 7.1 User Requirements and Scenarios (Task Lead: UPC [44])

- Task 7.2 Patent corpora (Task Lead: UPC [44])

- Task 7.3 Grammars for the patent domain (Task Lead: UGOT [2])

- Task 7.4 Ontologies and document indexation (Task Lead: Ontotext [37])

- Task 7.5 Prototype (Task Lead: Ontotext [37])

- Task 7.6 SMT and Hybrid MT (Task Lead: UPC [44])

- Task 7.7 Prototype (user interface) (Tas Lead by Ontotext [37])

- Task 7.8 Human evaluation (Task Lead: TBD)

- Task 7.9 Patent Case Study: Final Report (Task Lead: UPC [44])

Month 10-15 plan

- Task 7.2 starts in M10 and is due to provide a first set of corpora at the end of M16. Final revision depends on the availability of the EPO data.

- Task 7.3 starts in M10 and is due to provide a preliminary report at the end of M16.

Month 16-21 plan

- Task 7.1 starts at M15 and is due to provide a preliminar version at the beginning of M17.

- Task 7.3 will produce a more complete report by the beginning of M19.

- Task 7.4 starts at M16 and is due to provide a description of the type of queries at the end of M16.

- Task 7.5 starts at M16 and is due to provide a description of the Prototype architecture at the end of M16.

- Task 7.6 starts along with WP5 [53] and will produce a SMT baseline for the Patents prototype.

- D7.1 deadline is M21.

User Requirements

ID:

7.1

Workpackage:

Case Study: Patents [55]

Assignees:

aarne.ranta [4]

Assignees:

meritxell.gonzalez [56]

Status:

Assigned

Timeframe:

May 2011 - Oct 2011

Participants: All MOLTO [1] partners are requested to participate.

This task concerns the gathering of user requirements for the WP7 [55] Patent Case Study and the definition of the WP scenarios as requested by the reviewers.

Patent Corpora

ID:

7.2

Workpackage:

Case Study: Patents [55]

Task leader:

meritxell.gonzalez [56]

Assignees:

cristina.españa [57]

Assignees:

lluis.marquez [58]

Status:

Ongoing

Timeframe:

Jun 2011 - Mar 2012

Determining and gathering of bilingual and monolingual corpora for the patent case study.

Grammars for the patent domain

ID:

7.3

Workpackage:

Case Study: Patents [55]

Task leader:

ramona.enache [11]

Assignees:

aarne.ranta [4]

Assignees:

ramona.enache [11]

Status:

Ongoing

Timeframe:

Jan 2011 - May 2012

Ontologies and Document Indexation

ID:

7.4

Workpackage:

Case Study: Patents [55]

Task leader:

meritxell.gonzalez [56]

Assignees:

borislav.popov [35]

Assignees:

mariana.damova [59]

Dependencies:

Grammars for the patent domain [60]

Status:

Planned

Timeframe:

Jun 2011 - May 2012

Developing an ontology capturing the structure of patent documents; and indexing the patents documents according to the semantic knowledge.

Patents Retrieval System

ID:

7.5

Workpackage:

Case Study: Patents [55]

Task leader:

lluis.marquez [58]

Assignees:

borislav.popov [35]

Assignees:

milen.chechev [61]

Assignees:

petar [62]

Relevant Deliverables:

Patent Case Study Final Report [63]

Relevant Deliverables:

Patent MT and Retrieval Prototype [64]

Relevant Deliverables:

Patent MT and Retrieval Prototype Beta [65]

Dependencies:

Grammars for the patent domain [60]

Dependencies:

Ontologies and Document Indexation [66]

Dependencies:

Patent Corpora [67]

Status:

Ongoing

Timeframe:

Jun 2011 - Nov 2011

Contact @UPC [44]: Lluis and Cristina

DEPENDENCIES:

- TASK 1, 2, 3 and 4

- WP4 [54]. Knowledge Engineering

- TASK 8 (for final version of prototype)

Participants:

- Ontotext [37],

- UGOT [2],

- UPC [44]

Contact point @Ontotext [37]: Borislav Popov

DEADLINES: Beta = M21; Final = M27

Machine Translation Systems

ID:

7.6

Workpackage:

Case Study: Patents [55]

Assignees:

aarne.ranta [4]

Assignees:

cristina.españa [57]

Assignees:

lluis.marquez [58]

Assignees:

meritxell.gonzalez [56]

Assignees:

ramona.enache [11]

Relevant Deliverables:

Patent Case Study Final Report [63]

Relevant Deliverables:

Patent MT and Retrieval Prototype [64]

Relevant Deliverables:

Patent MT and Retrieval Prototype Beta [65]

Dependencies:

Grammars for the patent domain [60]

Status:

Ongoing

Timeframe:

Jan 2012 - May 2012

Contact @UPC [44]: Lluis and Cristina

DEPENDENCIES:

- TASK 2, 3

- WP5 [53]. A baseline of the WP5 [53] system will be integrated in the prototype.

Patents abstracts and claim are translated using the baseline of the hybrid system.

Protoype (User Interface)

ID:

7.7

Workpackage:

Case Study: Patents [55]

Task leader:

borislav.popov [35]

Assignees:

borislav.popov [35]

Assignees:

cristina.españa [57]

Assignees:

lluis.marquez [58]

Assignees:

meritxell.gonzalez [56]

Assignees:

milen.chechev [61]

Relevant Deliverables:

Patent MT and Retrieval Prototype [64]

Relevant Deliverables:

Patent MT and Retrieval Prototype Beta [65]

Dependencies:

Machine Translation Systems [68]

Dependencies:

Patents Retrieval System [69]

Status:

Planned

Timeframe:

Jun 2011 - May 2012

DEPENDENCIES:

- TASK 1

- TASK 8 (for final version of prototype)

Participants:

- Ontotext [37],

- UGOT [2],

- UPC [44]

Contact point @Ontotext [37]: Borislav Popov

DEADLINES: Beta = M21; Final = M27

Human evaluation

ID:

7.8

Workpackage:

Case Study: Patents [55]

Assignees:

lauri.carlson [36]

Dependencies:

Protoype (User Interface) [70]

Status:

Planned

DEPENDENCIES:

- TASK 5

Note: Deadlines have been delayed 3 months due to the WP delay.

DEADLINE: M31 (to allow for final report)

Subtasks

- Preparation starts M19 (at the very latest)

- Hiring translators

- Producing guidelines for translators

- Full evaluation starts at latest M28

- Evaluation will make use of the TAUS criteria

TAUS Evaluation Criteria:

- Excellent (4):

- Accurately transfers all info; correct terminology, correct grammar. Understanding not improved by reading the source text.

- Good (3):

- Contains minor mistakes; would not need to refer to source text to correct the mistakes.

- Medium (2):

- Significant errors in output. Would need to read the source text to correct the errors.

- Poor (1):

- Serious errors in output. Would need to read the source text to understand the output. Would probably need to retranslate from scratch.

Final report

ID:

7.9

Workpackage:

Case Study: Patents [55]

Assignees:

aarne.ranta [4]

Assignees:

meritxell.gonzalez [56]

Relevant Deliverables:

Patent MT and Retrieval Prototype [64]

Relevant Deliverables:

Patent MT and Retrieval Prototype Beta [65]

Dependencies:

Human evaluation [71]

Dependencies:

Machine Translation Systems [68]

Dependencies:

Patents Retrieval System [69]

Dependencies:

Protoype (User Interface) [70]

Status:

Planned

DEPENDENCIES:

- TASK 5, 6, 7, 8

WP8: Case Study: Cultural Heritage

The work is started by a study of the existing categorizations and metadata schemas adopted by the museum, as well as a corpus of texts in the current documentation which describe these objects (D8.1, UGOT [2] and Ontotext [37]). We will transform the CIDOC-CRM model into an ontology aligning it with the upper-level one in the base knowledge set (WP4 [54]) and modeling the museum object metadata as a domain specific knowledge base. Through the interoperability engine from WP4 [54] and the IDE from WP2 [10], we will semi-automatically create the translation grammar and further extend it (D8.2, UGOT [2], UHEL [38], UPC [44], Ontotext [37]). The final result will be an online system enabling museum (virtual) visitors to use their language of preference to search for artefacts through semantic (structured) and natural language queries and examine information about them. We will also automatically generate a set of articles in the Wikipedia format describing museum artefacts in the 5 languages with extensive grammar coverage (D8.3, UGOT [2], Ontotext [37]).

Links to Swedish museum databases who use the Carlotta system which is built upon the CIDOC-CRM model:

http://samsok.kmmuseum.se/ [72]

http://carlotta.gotlib.goteborg.se/pls/carlotta/welcome [73]

http://www.tremil.se/pls/hborg/rigby.welcome [74]

http://collections.smvk.se/pls/em/rigby.SokEnkel [75]

WP9: User Requirements and Evaluation

Requirements for work

The work will start with collecting user requirements for the grammar development IDE (WP2 [10]), translation tools (WP3 [76]), and the use cases (WP6 [45]-8).

We will define the evaluation criteria and schedule in synchrony with the WP plans (D9.1). We will define and collect corpora including diagnostic and evaluation sets, the former, to improve translation quality on the way, and the latter to evaluate final results.

Corpus definitions

- Each corpus available for MOLTO [1] will be described by the providing project members.

- The corpora will be split for development, diagnostic and evaluation use.

- Contact persons will be named for questions and requests for each corpus.

- Storage places and access protocols to gain this specified corpus data will be defined.

Description of end-user workflow

Translator's new role (parallel to WP3 [76]: Translator's tools) will be designed and described in the D9.1 deliverable. Most current translator's workbench software treat the original text as read-only source. The tools to be developed within WP3 [76] (+ 2) will lead towards more mutable role of source text. The translation process will resemble more like structured document editing or multilingual authoring than transformation from a fixed source to a number of target languages.

We will only provide a basic infrastructure API for external translation workbenches and keep an eye on the "new multilingual translator's workflow".

Introduction of WP liaison persons and other contacts

For each work package, the liaison contact information and work progress will be kept up-to-date on the MOLTO [1] web site. Our liaison person Mirka Hyvärinen [77] will be in contact with other project members.

Also possibility to access UHEL [38]'s internal working wiki "MOLTO [1] kitwiki [78]" will be granted upon request to other project members.

Evaluation of results

Evaluation aims at both quality and usability aspects. UHEL [38] will develop usability tests for the end-user human translator. The MOLTO [1]-based translation workflow may differ from the traditional translator's workflow. This will be discussed in the D9.1 evaluation plan.

To measure the quality of MOLTO [1] translations, we compare them to (i) statistical and symbolic machine translation (Google, SYSTRAN); and (ii) human professional translation. We will use both automatic metrics (IQmt and BLEU; see section 1.2.8 for details) and TAUS quality criteria (Translation Automation Users Society). As MOLTO [1] is focused on information-faithful grammatically correct translation in special domains, TAUS results will probably be more important.

Given MOLTO [1]'s symbolic, grammar-based interlingual approach, scalability, portability and usability are important quality criteria for the translation results. For the translator's tools, user-friendliness will be a major aspect of the evaluation. These criteria are quantified in (D9.1) and reported in the final evaluation (D9.2).

In addition to the WP deliverables, there will be continuous evaluation and monitoring with internal status reports according to the schedule defined in D9.1.

WP10: Dissemination and Exploitation

Define workplan here

- http://www.speaklike.com/products/ [79] some examples of applications

- http://www.sherpa.ac.uk/romeo/ [80] Publisher copyright policies & self-archiving

Factorize the Food grammar

ID:

10.3

Workpackage:

Dissemination and Exploitation [81]

Task leader:

aarne.ranta [4]

Assignees:

aarne.ranta [4]

Assignees:

olga.caprotti [5]

Status:

Completed

Completed on:

26 March, 2010 - 01:00

Factorize the grammar used now for the demo fridge in modules that isolate the different kinds of phrases: eg. Comments, Greetings, Questions, etc. Check whether there are ontologies that describe these.

The factorization can be seen in the phrasebook example under /example/phrasebook.

MOLTO Phrasebook May Release

ID:

10.4

Workpackage:

Dissemination and Exploitation [81]

Task leader:

aarne.ranta [4]

Assignees:

aarne.ranta [4]

Assignees:

krasimir.angelov [16]

Assignees:

olga.caprotti [5]

Assignees:

ramona.enache [11]

Assignees:

thomas.hallgren [26]

Dependencies:

Factorize the Food grammar [82]

Status:

Ongoing

Timeframe:

Apr 2010 - May 2010

The MOLTO [1] Phrasebook is a web application for the traveler, eventually it will be a phone application (for the Android). It consists of frequently used phrases that a foreigner might want to use when abroad.

Features of May Release

- fixes and additions in RGL

- data collection from

- wikipedia phrasebook

- wiki page for collection

- web server

- web GUI

- Android GUI

- structured and customizable release (e.g. choose the language pair)

- agree on base abstract syntax

- Android stand-alone

- complete remaining concretes

- examples + native informant

- feedback button

- current state info

- spam issue

- unlexing

- lexing &+

- disambiguation

- deletion

- history

- gr by shaking

demo preview: http://tournesol.cs.chalmers.se/~aarne/phrasebook/phrasebook.html [83]

WP11: Multilingual semantic wiki - AceWiki

Introduction

AceWiki is hosted at GitHub (https://github.com/AceWiki/AceWiki [84])

- Contributions to the AceWiki codebase can be made via GitHub pull requests (see http://help.github.com/send-pull-requests/ [85])

- Bugs can be reported via the AceWiki Issues list (https://github.com/AceWiki/AceWiki/issues [86])

- More mature feature requests can also be reported/assigned via the Issues list (the less mature should be brainstormed about here)

Tasks

- Task 11.1 [87]: Make the AceWiki design multilingual and implement a small AceWiki engine for multilingual GF [8] grammars

- Task 11.2 [88]: General refactoring of the AceWiki code

Meetings

- 13 December 2011 [89]

To do

Phase 1

AceWiki side:

- Refactor AceWiki to support different implementations of predictive parsers (at the moment, AceWiki's chartparser is hardwired) [done: Tobias]

- Extract from the package "aceowl" everything that should be reused in GFAceWiki into a new package (mostly OWL-related stuff) [done: Tobias]

- Connect AceWiki to GF [8] (via JPGF) [done: Tobias]

- Change the AceWiki architecture to support multilinguality [done: Tobias]

- Implement a simple AceWiki language engine for multilingual GF [8] grammars (as an alternative to the current ACE-OWL engine) [done: Tobias]

GF [8] side:

- Check the following three options of getting a multilingual OWL-capable ACE-implementation in GF [8] (there might be more options):

- Start with the official GF [8] implementation of ACE [assigned: Kaarel], see: https://github.com/Attempto/ACE-in-GF [90]

- Start with Normunds' GF [8] implementation of ACE [assigned: Kaarel] (discontinued), see: https://github.com/Kaljurand/AceWiki/tree/normunds/grammars/aceowl/normunds [91]

- Create a GF [8] implementation based on (parts of) the AceWiki grammar

- Create a stable multilingual OWL-capable ACE-implementation in GF [8]

Phase 2

- Implement support for adding/changing/deleting words

- Implement more languages

- Choose application domain(s) and build exemplary knowledge base

- Perform user studies

Releases

Release notes: https://raw.github.com/AceWiki/AceWiki/master/CHANGES.txt [92]

- 2012-01-05: v0.5.2

Unsorted

AceWiki as a webservice

See also https://github.com/yuchangyuan/AceWiki [93]

See also the thread starting with: https://lists.ifi.uzh.ch/pipermail/attempto/2011-December/000818.html [94]

- There could be potentially multiple front-ends

- the current front-end

- an existing GF [8] front-end

- Emacs

- Unix commandline

- ACE View

- native Android/iOS app

- ...

- REST API

- allows to easily push content (existing lexicon, existing ACE text) into the wiki

- should support GET as much as possible

- Make AceWiki easily deployable on hosting providers such as Google App Engine

- reasons: speed, reliability, etc.

- for that to work, AceWiki should be completely in Java (i.e. no using of APELocal), i.e. ape.exe would still have to be on a different host (because it is in Prolog)

- would reasoning performance profit in a major way?

AceWiki more configurable

- [done: Changyuan/Kaarel] Support APESocket and APEWebservice in addition to APELocal. Configuration at the XML file level. See also: http://attempto.ifi.uzh.ch/site/docs/java/ch/uzh/ifi/attempto/ape/ACEPar... [95]

AceWiki Refactoring

ID:

11.2

Workpackage:

Multilingual semantic wiki [96]

Assignees:

Kaarel.Kaljurand [97]

Assignees:

Tobias.Kuhn [98]

Relevant Deliverables:

Multilingual semantic wiki [99]

Status:

Completed

Timeframe:

Dec 2011 - Jan 2012

Completed on:

5 January, 2012 (All day)

General refactoring and clean-up of the AceWiki code.

Multilingual AceWiki

ID:

11.1

Workpackage:

Multilingual semantic wiki [96]

Assignees:

Tobias.Kuhn [98]

Relevant Deliverables:

Multilingual semantic wiki [99]

Status:

Completed

Timeframe:

Dec 2011 - Jan 2012

Completed on:

5 January, 2012 (All day)

Make the AceWiki design multilingual and implement a small AceWiki engine for multilingual GF [8] grammars.

WP12: Interactive knowledge-based systems

Ready to be edited.

Source URL: http://www.molto-project.eu/wiki/living-deliverables/d11-work-plan-molto

Links:

[1] http://www.molto-project.eu

[2] http://www.molto-project.eu/University of Gothenburg

[3] http://www.molto-project.eu/workplan/1

[4] http://www.molto-project.eu/users/aarneranta

[5] http://www.molto-project.eu/users/olgacaprotti

[6] http://www.molto-project.eu/workplan/deliverables/dissemination-plan-monitoring-and-assessment

[7] http://www.molto-project.eu/workplan/deliverables

[8] http://www.grammaticalframework.org

[9] http://code.google.com/p/grammatical-framework/

[10] http://www.molto-project.eu/workplan/2

[11] http://www.molto-project.eu/users/ramonaenache

[12] http://www.molto-project.eu/workplan/deliverables/gf-grammar-compiler-api

[13] http://www.molto-project.eu/workplan/tasks/designing-api-and-writing-its-documentation

[14] http://www.molto-project.eu/node/1212

[15] http://www.grammaticalframework.org/compiler-api/

[16] http://www.molto-project.eu/users/krasimirangelov

[17] http://www.molto-project.eu/workplan/deliverables/grammar-ide

[18] http://www.molto-project.eu/users/laurialanko

[19] http://www.molto-project.eu/users/jordisaludes

[20] http://yaml.org/

[21] http://en.wikipedia.org/wiki/GNU_build_system

[22] http://en.wikipedia.org/wiki/GLib

[23] http://pyyaml.org/

[24] http://www.nltk.org/

[25] http://www.haskell.org/ghc/

[26] http://www.molto-project.eu/users/thomashallgren

[27] http://www.molto-project.eu/workplan/tasks/release-gf-32

[28] http://www.grammaticalframework.org/demos/gfse/

[29] http://www.makeuseof.com/tag/top-3-browser-based-ides-code-cloud-2/

[30] http://groups.google.com/group/ymacs

[31] http://www.grammaticalframework.org/src/tools/gf.el

[32] https://bespin.mozillalabs.com/

[33] http://orc.csres.utexas.edu/tryorc.shtml#

[34] http://codemirror.net/

[35] http://www.molto-project.eu/users/borislavpopov

[36] http://www.molto-project.eu/users/lauricarlson

[37] http://www.molto-project.eu/Ontotext AD

[38] http://www.molto-project.eu/University of Helsinki

[39] http://www.molto-project.eu/node/858

[40] http://molto.ontotext.com

[41] http://www.w3.org/TR/rdf-sparql-query

[42] http://www.molto-project.eu/node/896

[43] http://www.molto-project.eu/node/948

[44] http://www.molto-project.eu/Universitat Politècnica de Catalunya

[45] http://www.molto-project.eu/workplan/6

[46] http://www.molto-project.eu/users/sebastian-xambo

[47] http://www.molto-project.eu/workplan/deliverables/simple-drill-grammar-library

[48] http://www.gnu.org/licenses/lgpl.html

[49] http://www.molto-project.eu/workplan/tasks/make-webalt-grammars-modular

[50] http://www.molto-project.eu/workplan/tasks/commanding-gf-library

[51] http://www.molto-project.eu/sites/default/files/Farm.thy

[52] http://www.molto-project.eu/workplan/9

[53] http://www.molto-project.eu/workplan/5

[54] http://www.molto-project.eu/workplan/4

[55] http://www.molto-project.eu/workplan/7

[56] http://www.molto-project.eu/users/meritxellgonzalez

[57] http://www.molto-project.eu/users/cristinaespa%C3%B1a

[58] http://www.molto-project.eu/users/lluismarquez

[59] http://www.molto-project.eu/users/marianadamova

[60] http://www.molto-project.eu/workplan/tasks/grammars-patent-domain

[61] http://www.molto-project.eu/users/milenchechev

[62] http://www.molto-project.eu/users/petar

[63] http://www.molto-project.eu/workplan/deliverables/patent-case-study-final-report

[64] http://www.molto-project.eu/workplan/deliverables/patent-mt-and-retrieval-prototype

[65] http://www.molto-project.eu/workplan/deliverables/patent-mt-and-retrieval-prototype-beta

[66] http://www.molto-project.eu/workplan/tasks/ontologies-and-document-indexation

[67] http://www.molto-project.eu/workplan/tasks/patent-corpora

[68] http://www.molto-project.eu/workplan/tasks/machine-translation-systems

[69] http://www.molto-project.eu/workplan/tasks/patents-retrieval-system

[70] http://www.molto-project.eu/workplan/tasks/protoype-user-interface

[71] http://www.molto-project.eu/workplan/tasks/human-evaluation

[72] http://samsok.kmmuseum.se/

[73] http://carlotta.gotlib.goteborg.se/pls/carlotta/welcome

[74] http://www.tremil.se/pls/hborg/rigby.welcome

[75] http://collections.smvk.se/pls/em/rigby.SokEnkel

[76] http://www.molto-project.eu/workplan/3

[77] http://www.molto-project.eu/user/36

[78] https://kitwiki.csc.fi/twiki/bin/view/MOLTO/WebHome

[79] http://www.speaklike.com/products/

[80] http://www.sherpa.ac.uk/romeo/

[81] http://www.molto-project.eu/workplan/10

[82] http://www.molto-project.eu/workplan/tasks/factorize-food-grammar

[83] http://tournesol.cs.chalmers.se/~aarne/phrasebook/phrasebook.html

[84] https://github.com/AceWiki/AceWiki

[85] http://help.github.com/send-pull-requests/

[86] https://github.com/AceWiki/AceWiki/issues

[87] http://www.molto-project.eu/workplan/tasks/multilingual-acewiki

[88] http://www.molto-project.eu/workplan/tasks/acewiki-refactoring

[89] http://www.molto-project.eu/node/1441

[90] https://github.com/Attempto/ACE-in-GF

[91] https://github.com/Kaljurand/AceWiki/tree/normunds/grammars/aceowl/normunds

[92] https://raw.github.com/AceWiki/AceWiki/master/CHANGES.txt

[93] https://github.com/yuchangyuan/AceWiki

[94] https://lists.ifi.uzh.ch/pipermail/attempto/2011-December/000818.html

[95] http://attempto.ifi.uzh.ch/site/docs/java/ch/uzh/ifi/attempto/ape/ACEParser.html

[96] http://www.molto-project.eu/workplan/11

[97] http://www.molto-project.eu/users/kaarelkaljurand

[98] http://www.molto-project.eu/users/tobiaskuhn

[99] http://www.molto-project.eu/workplan/deliverables/multilingual-semantic-wiki

Table of Contents

MOLTO Phrasebook May Release

Home

Printer-friendly

1

↩